Skip to content

Fix potential crash in FileReader.readAsArrayBuffer on malformed data URL#56382

Open
Nedunchezhiyan-M wants to merge 1 commit intofacebook:mainfrom
Nedunchezhiyan-M:fix/filereader-base64-null-safety
Open

Fix potential crash in FileReader.readAsArrayBuffer on malformed data URL#56382
Nedunchezhiyan-M wants to merge 1 commit intofacebook:mainfrom
Nedunchezhiyan-M:fix/filereader-base64-null-safety

Conversation

@Nedunchezhiyan-M
Copy link
Copy Markdown

@Nedunchezhiyan-M Nedunchezhiyan-M commented Apr 8, 2026

Summary

Fix a potential crash in FileReader.readAsArrayBuffer() when the native module returns a data URL string without a comma separator. The code splits on , and accesses index [1] without checking if it exists, which would pass undefined to toByteArray() and crash.

Added a nullish coalescing fallback to default to an empty string.

Changelog:

[GENERAL] [FIXED] - Fix potential crash in FileReader.readAsArrayBuffer when data URL has no comma separator

Test Plan

  1. The fix is defensive - in normal operation the native module returns a proper data URL with a comma
  2. With this fix, a malformed response produces an empty ArrayBuffer instead of a crash
  3. Existing FileReader behavior is unchanged for valid data URLs

… URL

When reading as ArrayBuffer, the code splits the data URL on ","
and accesses index [1] without a fallback. If the native module
returns a string without a comma, this results in undefined being
passed to toByteArray(), causing a crash.

Added nullish coalescing to default to an empty string.
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 8, 2026

Hi @Nedunchezhiyan-M!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@Nedunchezhiyan-M Nedunchezhiyan-M force-pushed the fix/filereader-base64-null-safety branch from e553a3d to 497e112 Compare April 8, 2026 19:59
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 10, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 10, 2026
@facebook-github-tools facebook-github-tools bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant